Repository navigation
Diagnose fenced JSON offline and remove placeholder paths from v3 prompt - #13
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The user reports 45 v2 final JSON-format errors and one output-limit error. The supplied response is fenced JSON and copies package/file.py from our schema example. This adds opt-in single-fence normalization with exact-source checks unchanged, and a CPU-only revalidation tool that preserves originals and exports only the final saved response, never the best retry.
Legacy v2 keeps strict parsing by default. A separate v3 runner/notebook uses a schema description without placeholder paths and explicitly grounds edits in pre-fix source headers. No new GPU run is needed to inspect saved v2 responses. Tests cover fences with outside prose, malformed/multiple fences, fabricated source/path rejection, source application, and post-hoc final-step selection and original-file preservation. No improvement or repaired task is claimed.